Cash letter print verification

ABSTRACT

A printed cash letter includes a machine-readable identifier, such as a barcode, identifying the cash letter. Upon printing, information from the identifier is read and stored in a first record. To determine whether the cash letter is a duplicate, a check presentment module compares information from the identifier with information in the first record. If information identifying the cash letter already exists in the first record, the cash letter is a duplicate. To verify cash letter printing, information identifying multiple cash letters to be printed is stored in a second record. Upon printing a portion of the cash letters, information read from identifiers on the printed cash letters is compared with information in the second record. If the second record includes information regarding a cash letter not identified in the information scanned from the barcodes, then the check presentment module identifies the cash letter as having not been printed.

RELATED PATENT APPLICATIONS

This patent application is related to U.S. patent application Ser. No.11/362,344, entitled “Cash Letter Print Streams With Audit Data,” filedFeb. 22, 2006, issued on Mar. 30, 2010 as U.S. Pat. No. 7,686,209, whichclaims priority under 35 U.S.C. §119 to U.S. Provisional PatentApplication No. 60/710,346, entitled “Image Replacement Document (IRD)Print Streams with Real-Time Audit Data,” filed Aug. 22, 2005, and U.S.Provisional Patent Application No. 60/657,142, entitled “CheckProcessing Using Substitute Check Images,” filed Feb. 28, 2005. Thispatent application also is related to co-pending U.S. patent applicationSer. No. 11/983,035, entitled “Identifying Duplicate Printed Paper CashLetters,” filed Nov. 6, 2007. The complete disclosure of theabove-identified applications is hereby fully incorporated herein byreference.

FIELD OF THE INVENTION

The invention relates generally to monitoring paper cash letterproduction and more particularly to verifying cash letter printing andidentifying duplicate printed paper cash letters.

BACKGROUND OF THE INVENTION

Effective Oct. 28, 2004, the Check Clearing for the 21st Century Act(“the Act”) improves the ability of banks to use electronic images ofpaper checks by, for example, submitting those images, along withassociated information, for electronic processing. Under the Act, if areceiving financial institution (“RI”) or its customer requires a papercheck, a paper image replacement document (“IRD”), such as a paper“substitute check,” may be created from an electronic check image andassociated electronic information. Under the Act, a substitute checkmeeting specified requirements is the legal equivalent of an originalpaper check, and an RI is required to accept the substitute check forpayment. This process enables banks to reduce the costs andinconveniences associated with physically handling and transportingoriginal paper checks.

Under the Act, the substitute check must be essentially an exact copy ofthe original paper check to be the legal equivalent of the originalpaper check. In particular, the substitute check must include an exactcopy of all of the Magnetic Ink Character Recognition (“MICR”) dataprovided on the original paper check and all check endorsements.

The terms “substitute check” and “IRD” generally are usedinterchangeably herein to refer to any electronic or paper document thatcan be used for electronic payment processing purposes, whether or notthe document is the legal equivalent of a paper check negotiableinstrument. The terms “bank” and “RI” generally are used herein to referto any party performing conventional or electronic check processing atany stage, including depositing and receiving institutions, theirnon-bank subsidiaries and affiliates, and any non-bank third partyagents that provide processing services to banks.

A “cash letter” is a collection of one or more bundles of checks and/orIRDs (interchangeably collectively or individually referred to herein as“items”) that can be transmitted from a bank to an RI. Further, as usedherein, a “cash letter” can comprise return items. A cash lettertypically includes a cover page comprising information regarding thecash letter's contents. For example, the cover page can comprise thenumber of items in the cash letter, information identifying thetransmitting bank, and/or information identifying the RI. For eachbundle of items in the cash letter, the cash letter can include a bundlesummary comprising the number of items in the bundle, the value of eachof the items in the bundle, and the total value of all items in thebundle. The cash letter also can include a cash letter bundle summarycomprising a total of the value of all the bundles in the cash letter.

A cash letter in electronic form, comprising images of the items andassociated financial data, is referred to herein as an “image cashletter” or “ICL.” A cash letter in paper form, comprising paper items,is referred to herein as a “paper cash letter.” The cover page, bundlesummaries, and cash letter bundle summary contained within a cashletter, whether paper or electronic, are collectively referred to hereinas “audit data.”

A bank can submit a cash letter to an RI either in electronic or paperform. For example, the bank can submit a paper cash letter to an RI viaconventional paper transport means, such as mail or truck delivery.Alternatively, the bank can communicate an ICL to an RI via anelectronic data transport means, such as a distributed computer network.

Conventionally, preparation of a paper cash letter, either by thesubmitting bank or the RI, generally required: (1) aggregating one ormore bundles of paper items (either original paper checks, substitutechecks, or other printed paper items); (2) printing a bundle summary foreach bundle; (3) printing a cash letter bundle summary for the cashletter; (4) printing a cover page for the cash letter; and (5)assembling the cash letter by matching the items to their respectivebundle summaries, matching the bundles to the cash letter bundlesummary, and matching the items, bundle summaries, and cash letterbundle summary to the cover page. Such preparation involves manyinefficiencies, most notably the delay involved in manually matching theitems, bundle summaries, cash letter bundle summary, and cover pagetogether to assemble the paper cash letter.

A recent approach for overcoming these inefficiencies includes producingprint streams for efficiently generating properly formatted and orderedpaper cash letters with substitute checks and audit data. Certainexemplary methods and systems for producing such print streams aredescribed in co-pending U.S. patent application Ser. No. 11/362,344,entitled “Cash Letter Print Streams With Audit Data,” the disclosure ofwhich is hereby fully incorporated herein by reference. To date, bankshave been unable to monitor the production of these print streams or theoutput of the corresponding paper cash letters.

In the traditional, paper processing arena, each paper cash lettercomponent could be seen and touched throughout processing. Determiningwhether a paper cash letter was produced simply required looking in oneor more trays at a bank processing station. Because Check 21 processingtakes place electronically, banks do not have physical points at whichthey can make such determinations. Oftentimes, this inability results infailure of some paper cash letters to be produced and other paper cashletters to be printed two or more times.

Thus, a need exists in the art for a system and method for monitoringpaper cash letter printing. Specifically, a need exists in the art for asystem and method for verifying paper cash letter printing and foridentifying duplicate printed paper cash letters.

SUMMARY OF THE INVENTION

The invention provides systems and methods for efficiently monitoringpaper cash letter printing. Specifically, the invention provides systemsand methods for verifying cash letter printing and identifying duplicateprinted paper cash letters

In a first record, a check presentment module stores informationregarding each of multiple ICLs to be printed. For example, the storedinformation can include information uniquely identifying each of theICLs, such as a total value of items in the cash letter, an AmericanBankers Association (“ABA”) number of a bank that will receive a printedcopy of the cash letter, a total number of item bundles in the cashletter, and a total number of items in the cash letter. The checkpresentment module generates a print stream for printing each of theICLs.

Included within the print stream is information for printing amachine-readable identifier, such as a barcode, for each of the ICLs.The machine-readable identifier includes information uniquelyidentifying the ICL associated therewith. For example, themachine-readable identifier can include at least a portion of theinformation stored in the first record.

At least a portion of the ICLs are printed. Each printed ICL includesits corresponding machine-readable identifier. For example, a cover pageof each printed ICL can include a barcode associated with the printedICL.

Upon printing, information from each of the machine-readable identifiersis read. The check presentment module stores information from themachine-readable identifiers in a second record. To determine whetherall of the ICLs have been printed, the check presentment module comparesthe information stored in the first record with the information storedin the second record. For example, if the first record includesinformation regarding an ICL, which is not identified in the secondrecord, then the check presentment module can determine that the ICL hasnot been printed.

In certain exemplary embodiments, the check presentment module canoutput an alert to notify an operator that the ICL has not been printed.For example, the alert can include information uniquely identifying theICL.

To determine whether a printed ICL is a duplicate, i.e., whether the ICLhas been printed two or more times, a check presentment module cancompare information from a machine-readable identifier of the printedICL with information stored in the second record. If informationidentifying the ICL already exists in the second record, then the checkpresentment module can determine that the ICL already has been printed,and thus, is a duplicate. In certain exemplary embodiments, the checkpresentment module can output an alert to notify an operator that theICL is a duplicate. For example, the alert can include informationuniquely identifying the ICL.

These and other aspects, objects, features, and advantages of theinvention will become apparent to those skilled in the art uponconsideration of the following detailed description of illustratedexemplary embodiments, which include the best mode of carrying out theinvention as presently perceived.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram depicting a system for processing checks,according to an exemplary embodiment of the invention.

FIG. 2 is a block diagram depicting a depositing institution of a systemfor processing checks, according to an exemplary embodiment of theinvention.

FIG. 3 is a block diagram depicting a capture site of a system forprocessing checks, according to an exemplary embodiment of theinvention.

FIG. 4 is a flow chart depicting a method for processing checks,according to an exemplary embodiment of the invention.

FIG. 5A and FIG. 5B are flow charts depicting a method for creating afinancial data file comprising expanded mass data sets, according to anexemplary embodiment of the invention

FIG. 6A and FIG. 6B are flow charts depicting a method for conducting areject/repair analysis of a financial data file using expanded mass datasets of the financial data file, according to an exemplary embodiment ofthe invention.

FIG. 7 is a flow chart depicting a method for presenting a check forpayment, according to an exemplary embodiment of the invention.

FIG. 8 is a flow chart depicting a method for generating a cash letterprint stream, according to an exemplary embodiment of the invention.

FIG. 9 is a block diagram depicting a print stream generated inaccordance with an exemplary embodiment of the invention.

FIG. 10 is a block diagram depicting a cover page printed from a printstream generated in accordance with an exemplary embodiment of theinvention.

FIG. 11 is a block diagram depicting a bundle summary page printed froma print stream generated in accordance with an exemplary embodiment ofthe invention.

FIG. 12 is a block diagram depicting a substitute check page printedfrom a print stream generated in accordance with an exemplary embodimentof the invention.

FIG. 13 is a block diagram depicting a cash letter bundle summary pageprinted from a print stream generated in accordance with an exemplaryembodiment of the invention.

FIG. 14 is a block diagram depicting an exception report page printedfrom a print stream generated in accordance with an exemplary embodimentof the invention.

FIG. 15 is a flow chart depicting a method for verifying cash letterprinting, according to an exemplary embodiment of the invention.

FIG. 16 is a flow chart depicting a method for identifying duplicateprinted paper cash letters, according to an exemplary embodiment of theinvention.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

The invention is directed to systems and methods for processing checksunder the Check Processing Under the Check Clearing For The 21^(st)Century Act (“the Act”). In particular, the invention is directed tosystems and methods for producing print streams for efficientlygenerating properly formatted and ordered paper cash letters comprisingsubstitute checks and audit data. By using expanded fields (alsoreferred to herein as “expanded mass data sets”) of a financial datafile, each substitute check can comprise all of the MICR data andaddenda data provided on a corresponding, original paper check. Thus,each substitute check can comprise all of the information necessary tocomply with the requirements of the Act.

In accordance with an exemplary embodiment of the invention, a printstream file can comprise electronic form definitions for each documentto be printed in the cash letter. For example, the cash letter documentscan include a cover page, one or more bundles of substitute checks, abundle summary for each substitute check bundle, a cash letter bundlesummary, and/or an exception report page. A check presentment module canparse and store information from an electronic image cash letter file indata fields of the print stream file's electronic form definitions.Printing the information in the print stream file results in a properlyformatted and ordered paper cash letter comprising substitute checks andaudit data. The audit data comprises the cover page, bundlesummary(ies), cash letter bundle summary, and/or exception report page,which can each detail the documents printed concurrently therewith.

The invention comprises a computer program that embodies the functionsdescribed herein and illustrated in the appended flow charts. However,it should be apparent that there could be many different ways ofimplementing the invention in computer programming, and the inventionshould not be construed as limited to any one set of computer programinstructions. Further, a skilled programmer would be able to write sucha computer program to implement an embodiment of the disclosed inventionbased on the flow charts and associated description in the applicationtext. Therefore, disclosure of a particular set of program codeinstructions is not considered necessary for an adequate understandingof how to make and use the invention. The inventive functionality of theclaimed computer program will be explained in more detail in thefollowing description read in conjunction with the figures illustratingthe program flow.

Turning now to the drawings, in which like numerals indicate likeelements throughout the figures, exemplary embodiments of the inventionare described in detail.

An exemplary system for processing checks will now be described withreference to FIGS. 1-3. FIG. 1 is a block diagram depicting a system 100for processing checks, according to an exemplary embodiment of theinvention. FIG. 2 is a block diagram depicting a depositing institution103 of the system 100, according to an exemplary embodiment of theinvention. FIG. 3 is a block diagram depicting a capture site 104 of thesystem 100, according to an exemplary embodiment of the invention.

The system 100 comprises various financial institutions and computersystems involved in check processing. In particular, the system 100comprises the depositing institution 103, the capture site 104, a checkprocessing site 105, and a receiving institution 125. The depositinginstitution 103 collects paper checks from a customer. Then, thedepositing institution 103 can bundle the paper checks in one or morepaper cash letters. Each paper cash letter can comprise one or morebundles of original paper checks and paper image replacement documents,such as substitute checks. The depositing institution 103 forwards thepaper checks to the capture site 104 or the check processing site 105for electronic processing.

Alternatively, the depositing institution 103 can itself generate anelectronic image cash letter (“ICL”) based on the paper checks. Thedepositing institution 103 can forward the generated ICL to the checkprocessing site 105 for electronic processing. The ICL can be anelectronic file that complies with the American National StandardsInstitute Specifications for Electronic Exchange of Check and Image Data(ANSI X9.37/X9.100), or other appropriate industry standards, as maychange from time to time. The ICL can comprise, for each paper check,one or more electronic images of the check, all of the complete MICRdata provided on the check, and additional financial data related to thecheck.

The ICL can further comprise a series of records related to the checks.For example, for each bundle of checks in the ICL, the ICL can include abundle summary control record comprising information about the bundle,such as a bundle identification number, the number of items in thebundle, the value of each of the checks in the bundle, and the totalvalue of all the checks in the bundle. The ICL also can comprise a coverpage control record comprising information about the origin anddestination of the ICL, and a cash letter bundle summary control recordcomprising a summary of all bundle summary control records in the ICL.

Thus, in alternative embodiments of the invention, the depositinginstitution 103 can (1) generate an ICL for received checks and forwardthe ICL to the check processing site 105, (2) forward received paperchecks to the capture site 104, or (3) forward received paper checks tothe check processing site 105.

The following description discusses an embodiment in which thedepositing institution 103 forwards received paper checks to the checkprocessing site 105 via a conventional paper cash letter. The checkprocessing site 105 receives the paper checks from the depositinginstitution 103. A sorter 107 of the check processing site 105electronically captures financial data from each received paper check.The sorter 107 comprises an image capture device (not shown), such as ascanner or camera, which captures at least one electronic image of eachcheck. For example, the sorter 107 can capture, for each check, an imageof the front of the check and an image of the back of the check. Uponimage capture, the sorter 107 forwards each image to a data capturemodule 111 of a check processor 109 for further processing. The datacapture module 111 stores the electronic image(s) in one or more imagefiles, which the data capture module 111 maintains in an image filedatabase 113 of the check processor 109. In one exemplary embodiment ofthe invention, the sorter 107 and the data capture module 111 can bepart of the same physical unit.

The sorter 107 further comprises a MICR reader (not shown) that readsthe MICR data from each check. Upon reading the MICR data, the sorter107 identifies additional financial data related to the check, which isincidental to the processing of the check. For example, the sorter 107can identify a unique item sequence number, a check processing siteidentifier, a processing date, a check amount, and/or a routing transitnumber of the depositing institution 103. The MICR data and additionalfinancial data are collectively referred to herein as “financial data.”The sorter 107 forwards the financial data to the data capture module111 for further processing.

The data capture module 111 stores a form financial data file withmultiple fields. For example, the data capture module 111 can store theform financial data file with data fields labeled F1-F7 and F10-F12. Thedata capture module 111 reads the financial data from the sorter 107 andparses and stores portions of the financial data in each of the datafields. For example, the data stored in fields F1-F7 of the financialdata file can comprise the check amount stored in field F1, processcontrol data stored in field F2, an account number stored in field F3, acheck number stored in field F4, a payor bank's routing transit numberstored in field F5, an external processing code stored in field F6, and“auxiliary on us” data stored in field F7. Fields F2-F4 are collectivelyreferred to herein as the “on us field.” The data in the on us field isreferred to herein as “on us data.”

Each of fields F1-F7 is respectively designed to accommodate a setnumber of characters without extraneous information such as dashes andfield delimiters or other items. Accordingly, prior to storing thefinancial data in the respective fields of the financial data file, thedata capture module 111 truncates all extraneous information and alldata beyond the allowed number of characters in each of those fields.The data capture module 111 typically truncates the data in fields F2,F3, F4, and F7.

The data stored in fields F10-F11 can comprise untruncated financialdata. For example, the data stored in fields F10-F11 can compriseuntruncated on us data stored in field F10 and untruncated auxiliary onus data stored in field F11. Thus, the fields of the financial data filecan comprise all of the MICR data from the original paper check.

The check processor 109 also comprises an image quality analysis module110, which can evaluate the quality of each captured check image.Certain exemplary systems and methods for performing such an evaluationare described in co-pending U.S. patent application Ser. No. 11/079,120,entitled “Assessing Electronic Image Quality,” the disclosure of whichis hereby fully incorporated herein by reference. The image qualityanalysis module 110 communicates the results of the evaluation to thedata capture module 111. The data capture module 111 stores the imagequality analysis results in a field of the financial data file, such asfield F12. Then, the data capture module 111 stores the financial datafile in a financial data file database 114 of the check processor 109.

In one embodiment of the invention, the image quality analysis module110 can store additional data related to the image quality analysisresults in field F12 of the financial data file. For example, the imagequality analysis module 110 can store a reason for an image qualityanalysis result in field F12. In addition, an indicator can be stored infield 12 to indicate whether the image(s) corresponding to the data infield F12 has(have) corresponding addenda data.

The functionality of the data capture module 111 is described in moredetail below with reference to FIGS. 5A and 5B.

The check processor 109 further comprises an addenda data module 112,which generates and/or captures electronic addenda data for each check.For example, the addenda data can comprise a bank endorsement. Theaddenda data module 112 inputs the addenda data into one or more addendadata files. The addenda data module 112 stores the addenda data file(s)in an addenda data file database 115 of the check processor 109.

For each check, the data capture module 111 associates the correspondingimage file(s), financial data file, and addenda data file(s) for furtherprocessing. For example, the data capture module 111 can associate theimage file(s), the financial data file, and the addenda data file(s) fora check with a common sequence number, identification number, or othersuitable data link known in the art.

The check processor 109 further comprises a reject/repair module 118,which can verify, for each check, the contents of the image file(s) andthe financial data file. The reject/repair module 118 analyzes thefinancial data file for errors. For example, the reject/repair module118 might detect an error if a field of the financial data file is emptyor if it comprises a character or string that is not in the properformat. If an error is detected, the reject/repair module 118 presentsthe image file(s) and certain of the associated financial data from thefinancial data file on a display 119 for viewing by a user. In anexemplary embodiment, the display 119 can be a computer monitor oranother device suitable for presenting images and textual data to theuser.

The reject/repair module 118 presents the financial data from fields F1,F5, and F6 of the financial data file on the display 119. Thereject/repair module 118 also presents the complete on us data fromfield F10 in place of the truncated on us data in data fields F2, F3,and F4 on the display 119. The reject/repair module 118 further presentsthe complete auxiliary on us data from field F11 in place of thetruncated auxiliary on us data in data field F7 on the display 119.Thus, the display 119 presents the user with the complete MICR data fromthe original paper check.

The user compares the presented financial data with the presented imagefile(s) and corrects any errors in the financial data via a keyboard 120or other suitable input device known in the art. For example, where adisplayed data field is empty or incorrect but the displayed image ofthe check comprises data corresponding to the data field, the user canenter the financial data from the displayed image into the displayeddata field.

Then, the reject/repair module 118 stores the complete, correctedauxiliary on us data displayed in field F7 in field F11 of the financialdata file. The reject/repair module 118 further stores the complete,corrected on us data displayed in fields F2, F3, and F4 in field F10 ofthe financial data file. In one embodiment of the invention, thereject/repair module 118 truncates the data in each corrected field, inaccordance with the requirements of each of data fields F2, F3, F4, andF7. Then, the reject/repair module 118 stores the corrected, truncateddata in the corresponding fields of the financial data file.

The functionality of the reject/repair module 118 is described in moredetail below with reference to FIGS. 6A and 6B.

The check processor 109 further comprises a check presentment module116, which is operable to present each received check to the receivinginstitution 125 for payment. The check presentment module 116 cangenerate a substitute check file for each check. In an exemplaryembodiment, the substitute check file can comprise the check'selectronic image(s), the check's financial data, and the check's addendadata. The check presentment module 116 stores the substitute check filein a substitute check database 108 of the check processor 109.

The check presentment module 116 can create at least one ICL comprisingthe substitute check file(s). Depending on the preferences of thereceiving institution 125, the check presentment module 116 can presentthe ICL electronically or via paper. For example, the check presentmentmodule 116 can electronically transmit the ICL via a network (notillustrated) to an RI computer 126 of the receiving institution 125.

Alternatively, the ICL can be locally or remotely printed for paperdelivery. For example, the check presentment module 116 can locallyprint the ICL on a printer 117 of the check processing site 105. Thecheck presentment module 116 can prepare a print stream comprising theICL. The check presentment module 116 can transmit the print stream tothe printer 117 for printing. An operator at the check processing site105 can collect one or more of the printed ICLs for delivery to thereceiving institution 125. Alternatively, the check presentment module116 can generate, and transmit to the receiving institution 125, a printstream by which the receiving institution 125 can print the ICL on an RIPrinter 127.

In an alternative exemplary embodiment of the invention, the checkpresentment module 116 can generate an ICL print stream without firstgenerating an ICL or a substitute check file. The check presentmentmodule 116 can collect data directly from the image file database 113,the financial data file database 114, and/or the addenda data filedatabase 112 for creation of the print stream. The check presentmentmodule 116 can store the collected data in pre-defined fields of a printstream file and transmit the print stream file to the printer 117 or theRI printer 127 for printing.

The functionality of the check presentment module 116 is described inmore detail below with reference to FIG. 8.

A person of skill in the art will recognize that the image file database113, the financial data file database 114, the addenda data filedatabase 115, and the substitute check database 108 can be part of thesame physical unit, a single database, or separate components.

In an alternative exemplary embodiment, the depositing institution 103can forward original or substitute paper checks to the capture site 104associated with the check processing site 105. Although only one capturesite 104 is illustrated in FIG. 1, multiple capture sites can beassociated with the check processing site 105. The capture site 104 canperform the check image and financial data capture process and canforward the captured images and data to the check processing site 105.

The capture site 104 receives paper checks from the depositinginstitution 103 and processes each paper check via a sorter 307. Thesorter 307 comprises an image capture device (not shown), such as ascanner or camera, which captures at least one electronic image of eachcheck. For example, the sorter 307 can capture, for each check, an imageof the front of the check and an image of the back of the check. Uponimage capture, the sorter 307 forwards each image to a CS data capturemodule 311 of a CS check processor 309 for further processing. The CSdata capture module 311 stores the electronic image(s) in one or moreimage files, which the CS data capture module 311 maintains in adatabase 310 of the CS check processor 309.

The sorter 307 further comprises a MICR reader (not shown) that readsthe MICR data from each check. Upon reading the MICR data, the sorter307 identifies additional financial data related to the check, which isincidental to the processing of the check. For example, the sorter 307can identify a unique item sequence number, a check processing siteidentifier, a processing date, a check amount, and/or a routing transitnumber of the depositing institution 103. The sorter 307 forwards thefinancial data to the CS data capture module 311 for further processing.In one exemplary embodiment of the invention, the sorter 307 and the CSdata capture module 311 can be part of the same physical unit.

The CS data capture module 311 stores a form financial data file withmultiple fields. For example, the CS data capture module 311 can storethe form financial data file with fields F1-F7 and F10-F12. The CS datacapture module 311 reads the financial data from the sorter 307 andparses and stores portions of the financial data in each of the datafields. For example, the CS data capture module 311 can store truncatedfinancial data in fields F1-F7 of the financial data file. The CS datacapture module 311 can further store untruncated financial data infields F10-F11 of the financial data file. The fields of the financialdata file can comprise all of the MICR data from the original papercheck. The CS data capture module 311 stores the financial data file inthe database 310.

The CS check processor 309 further comprises a reject/repair module 313,which can verify, for each check, the contents of the image file(s) andthe financial data file. The reject/repair module 313 analyzes thefinancial data file for errors. For example, the reject/repair module313 might detect an error if a field of the financial data file is emptyor if it comprises a character or string that is not in the properformat. If an error is detected, the reject/repair module 313 presentsthe image file(s) and certain of the associated financial data from thefinancial data file on a display 319 for viewing by a user. In anexemplary embodiment, the display 319 can be a computer monitor oranother device suitable for presenting images and textual data to theuser.

The reject/repair module 313 presents the financial data from fields F1,F5, and F6 of the financial data file on the display 319. Thereject/repair module 313 also presents the complete on us data fromfield F10 in place of the truncated on us data in fields F2, F3, and F4on the display 319. The reject/repair module 313 further presents thecomplete auxiliary on us data from field F11 in place of the truncatedauxiliary on us data in field F7 on the display 319. Thus, the display319 presents a user with all of the MICR data from the original papercheck.

The user compares the presented financial data with the presented imagefile(s) and corrects any errors in the financial data via a keyboard 320or other suitable input device known in the art. For example, where adisplayed data field is empty or incorrect but the displayed image ofthe check comprises data corresponding to the data field, the user canenter the financial data from the displayed image into the displayeddata field.

Then, the reject/repair module 313 stores the complete, correctedauxiliary on us data displayed in field F7 in field F11 of the financialdata file. The reject/repair module 313 further stores the complete,corrected on us data displayed in fields F2, F3, and F4 in field F10 ofthe financial data file. In one embodiment of the invention, thereject/repair module 313 can truncate the data in each corrected field,in accordance with the requirements of each of fields F2, F3, F4, andF7. Then, the reject/repair module 313 stores the corrected, truncateddata in corresponding fields of the financial data file.

The functionality of the reject/repair module 313 is described in moredetail below with reference to FIGS. 6A and 6B.

For each check, the CS data capture module 311 can forward theelectronic image(s) of the check and the check's financial data to thedata capture module 111 of the check processing site 105 for furtherprocessing, as discussed above with reference to FIG. 1. In this case,the forwarded data can be stored in the appropriate database(s) and canbe accessed via the check presentment module 116 to prepare therequested form of presentment to the receiving institution 125. At thecheck processing site 105, the data capture module 111 processes thefinancial data and images for presentment to the receiving institution125.

In another alternative exemplary embodiment, the depositing institution103 can create an ICL based on the paper checks and can communicate theICL to the check processing site 105. In this case, the depositinginstitution 103 can comprise components similar to those of the checkprocessing site 105.

The depositing institution 103 processes paper checks at a sorter 207.The sorter 207 electronically captures information from each papercheck. The sorter 207 comprises an image capture device (not shown),such as a scanner or camera, which captures at least one electronicimage of each check. For example, the sorter 207 can capture, for eachcheck, an image of the front of the check and an image of the back ofthe check. Upon image capture, the sorter 207 forwards each image to aDI data capture module 211 of a DI check processor 209 for furtherprocessing. The DI data capture module 211 can store the electronicimage(s) in one or more image files, which the depositing institutiondata capture module 211 maintains in a database 210 of the DI checkprocessor 209. In one exemplary embodiment of the invention, the sorter207 and the DI data capture module 211 can be part of the same physicalunit.

The sorter 207 further comprises a MICR reader (not shown) that readsthe MICR data from each check. Upon reading the MICR data, the sorter207 identifies additional financial data related to the check, which isincidental to the processing of the check. For example, the sorter 207can identify a unique item sequence number, a check processing siteidentifier, a processing date, a check amount, and/or a routing transitnumber of the depositing institution 103. The sorter 207 forwards thefinancial data to the DI data capture module 211 for further processing.

The DI data capture module 211 stores a form financial data file withmultiple fields. For example, the DI data capture module 211 can storethe form financial data file with fields F1-F7 and F10-F12. The DI datacapture module 211 reads the financial data from the sorter 207 andparses and stores portions of the financial data in each of the datafields. For example, the DI data capture module 211 can store truncatedfinancial data in fields F1-F7 of the financial data file. The DI datacapture module 211 can further store untruncated financial data infields F10-F11 of the financial data file. The fields of the financialdata file can comprise all of the MICR data from the original papercheck. The DI data capture module 211 stores the financial data file inthe database 210.

The DI check processor 209 further comprises an addenda data module 212,which generates and/or captures electronic addenda data for each check.For example, the addenda data can comprise a bank endorsement. Theaddenda data module 212 inputs the addenda data into one or more addendadata files. The addenda data module 212 stores the addenda data file(s)in the database 210.

For each check, the DI data capture module 211 associates thecorresponding image file(s), financial data file, and addenda datafile(s) for a check with a sequence number, identification number, orother suitable data link known in the art.

The DI check processor 209 further comprises a reject/repair module 213,which can verify, for each check, the contents of the image file(s) andthe financial data file. The reject/repair module 213 analyzes thefinancial data file for errors. For example, the reject/repair module213 might detect an error if a field of the financial data file is emptyor if it comprises a character or string that is not in the properformat. If an error is detected, the reject/repair module 213 presentsthe image file(s) and certain of the associated financial data from thefinancial data file on a display 219 for viewing by a user. In anexemplary embodiment, the display 219 can be a computer monitor oranother device suitable for presenting images and textual data to theuser.

The reject/repair module 213 presents the financial data from fields F1,F5, and F6 of the financial data file on the display 219. Thereject/repair module 213 also presents the complete on us data fromfield F10 in place of the truncated on us data in fields F2, F3, and F4on the display 219. The reject/repair module 213 further presents thecomplete auxiliary on us data from field F11 in place of the truncatedauxiliary on us data in field F7 on the display 219. Thus, the display219 presents the user with the complete MICR data from the originalpaper check.

The user compares the presented financial data with the presented imagefile(s) and corrects any errors in the financial data via a keyboard 220or other suitable input device known in the art. For example, where adisplayed data field is empty or incorrect but the displayed image ofthe check comprises data corresponding to the data field, the user canenter the financial data from the displayed image into the displayeddata field.

Then, the reject/repair module 213 stores the complete, correctedauxiliary on us data displayed in field F7 in field F11 of the financialdata file. The reject/repair module 213 further stores the complete,corrected on us data displayed in fields F2, F3, and F4 in field F10 ofthe financial data file. In one embodiment of the invention, thereject/repair module 213 truncates the data in each corrected field, inaccordance with the requirements of each of fields F2, F3, F4, and F7.Then, the reject/repair module 213 stores the corrected, truncated datain the corresponding fields of the financial data file.

The functionality of the reject/repair module 213 is described in moredetail below with reference to FIGS. 6A and 6B.

The DI check processor 209 further comprises an ICL module 215, whichgenerates at least one ICL comprising information regarding one or morebundles of checks. Each bundle can comprise one or more checks. For eachcheck, the ICL can include the electronic image(s) from the check'simage file(s), the financial data from the check's financial data file,and the addenda data from the check's addenda data file.

The ICL can further comprise a series of records related to the checks.For example, for each bundle of checks in the ICL, the ICL can include abundle summary control record comprising information about the bundle,such as a bundle identification number, the number of items in thebundle, the value of each of the checks in the bundle, and the totalvalue of all the checks in the bundle. The ICL also can comprise a coverpage control record comprising information about the origin anddestination of the ICL, and a cash letter bundle summary control recordcomprising a summary of all bundle summary control records in the ICL.The DI check processor 209 can forward the ICL to the data capturemodule 111 of the check processing site 105 for further processing.

Those skilled in the art will appreciate that exemplary system 100 ismerely representative of the components for processing checks. Otherembodiments of the invention may not have all of the componentsidentified in FIGS. 1-3 or can include additional components.

FIG. 4 is a flow chart depicting a method 400 for processing checks,according to an exemplary embodiment of the invention. The exemplarymethod 400 is illustrative and, in alternative embodiments of theinvention, certain steps can be performed in a different order, inparallel with one another, or omitted entirely, and/or certainadditional steps can be performed without departing from the scope andspirit of the invention. The method 400 is described below withreference to FIGS. 1 and 4.

In step 402, the check processing site 105 receives a conventional papercash letter comprising original and/or substitute paper checks from thedepositing institution 103. At the check processing site 105, the paperchecks are initially processed via the sorter 107. In step 405, thesorter 107 selects a check for processing. In step 410, the sorter 107captures at least one electronic image of the check. In an exemplaryembodiment, the sorter 107 captures an image of the front of the checkand an image of the back of the check. In step 415, the sorter 107communicates the captured electronic image(s) to the data capture module111, which creates at least one image file comprising the electronicimage(s). In step 420, the data capture module 111 stores the imagefile(s) in the image file database 113.

In step 425, the data capture module 111, in conjunction with the sorter107 and the image quality analysis module 110, creates a financial datafile comprising information regarding the check. For example, thefinancial data file can comprise the check's financial data and theresults of an image quality analysis performed on the capturedelectronic image(s) of the check. Step 425 is described in more detailbelow with reference to FIG. 5. In step 430, the data capture module 111stores the financial data file in the financial data file database 114.

In step 435, the addenda data module 112 creates an addenda data filecomprising addenda data for the check. The addenda data module 112 cangenerate and/or capture the addenda data from the check. In an exemplaryembodiment, the addenda data can comprise a bank endorsement, a checkprocessing date, a processing sequence number, and/or an image qualityrecord. In step 440, the addenda data module 112 stores the addenda datafile in the addenda data file database 115.

In step 445, the data capture module 111 associates the check's imagefile(s), financial data file, and addenda data file(s) with each other.For example, the data capture module 111 can associate the imagefile(s), the financial data file, and the addenda data file(s) via acommon sequence number, identification number, file name, or othersuitable data link known in the art.

In step 450, the reject/repair module 118 conducts a reject/repairanalysis of the check's financial data file. The reject/repair module118 allows detection and correction of certain errors in the financialdata file. Step 450 is discussed in more detail below with reference toFIGS. 6A and 6B.

In step 455, the sorter 107 determines whether to select another checkfor image/financial data capture. If so, the method 400 branches back tostep 405 to repeat the image/financial data capture of another check. Ifthe sorter 107 will not select another check, then the method 400branches to step 460 to present the selected check(s) for payment. Step460 is described in more detail below with reference to FIG. 7.

FIG. 5A and FIG. 5B are flow charts depicting a method 425 for creatinga financial data file comprising expanded mass data sets, according toan exemplary embodiment of the invention, as referred to in step 425 ofFIG. 4. The exemplary method 425 is merely illustrative and, inalternative embodiments of the invention, certain steps can be performedin a different order, performed in parallel with one another, or omittedentirely, and/or certain additional steps can be performed withoutdeparting from the scope and spirit of the invention. The method 425 isdescribed below with reference to FIGS. 1 and 5.

In step 503, a form financial data file is created with fields F1-F7 andF10-F12, and the form financial data file is stored by the data capturemodule 111. The data capture module 111 can configure fields F1-F7 ofthe form financial data file to receive truncated financial data. Forexample, the data capture module 111 can designate that Field F2 cannotinclude any dashes or other extraneous characters. The data capturemodule 111 can further designate that Field F2 can receive only up tothree bytes of data or a specified number of characters.

The fields F1-F7 correspond to the standard fields established by theAmerican National Standards Institute Specifications for ElectronicExchange of Check and Image Data (ANSI X9.37/X9.100), which establishthe specific type, format, and amount of data for each of those fields.Note that, in certain exemplary embodiments of the invention, the fieldsF1-F7 can correspond to other appropriate industry standards, as maychange from time to time. For example, the data stored in the financialdata file can comprise amount data stored in field F1, process controldata stored in field F2, account number data stored in field F3, checknumber data stored in field F4, routing transit number data stored infield F5, an external processing code stored in field F6, and auxiliaryon us data stored in field F7.

In step 505, the sorter 107 identifies financial data related to thepaper check. For example, the sorter 107 can read MICR data from thecheck and can identify other financial data that is incidental to theprocessing of the check. The MICR data can comprise a check amount,process control data, account number data, check number data, a payorbank's routing transit number, and auxiliary on us data. Additionally,the sorter 107 can identify a unique item sequence number, a checkprocessing site identifier, a processing date, and/or a routing transitnumber of the depositing institution 103.

In step 507, the sorter 107 transmits the identified financial data tothe data capture module 111. In step 510, the data capture module 111parses amount data from the financial data. The term “amount data” isused herein to refer to financial data that relates to the value of thecheck. For example, the amount data can comprise the U.S. dollar valueof the check, which can be expressed in cents. In step 513, the datacapture module 111 stores the amount data in field F1 of the financialdata file created in step 503.

In step 515, the data capture module 111 parses process control datafrom the financial data. The term “process control data” is used hereinto refer to a check number or transaction code that a bank uses toidentify an item or a group of items. In step 516, the data capturemodule 111 stores the process control data in field F10 of the financialdata file.

In step 517, the data capture module 111 truncates the process controldata to remove extraneous characters such as dashes and to remove excesscharacters, as required by field F2. For example, if field F2 only canreceive up to three bytes of data and the process control data is tenbytes long, the data capture module 111 can truncate seven bytes of datafrom the process control data. In step 518, the data capture module 111stores the truncated process control data in field F2 of the financialdata file.

In step 520, the data capture module 111 parses account number data fromthe financial data. The term “account number data” is used herein torefer to information related to the check payor's account at thereceiving institution. In step 521, the data capture module 111 storesthe account number data in field F10 of the financial data file, next tothe process control data stored in field F10 in step 516. In exemplaryembodiments, the account number data and the process control data infield F10 can be separated by a dash, colon, or other suitableseparator.

In step 522, the data capture module 111 truncates the account numberdata to remove extraneous characters such as dashes and to removeexcessive characters, as required by field F3. For example, if field F3only can receive up to eight bytes of data and the account number datais ten bytes long, the data capture module 111 can truncate two bytes ofdata from the account number data. In step 523, the data capture module111 stores the truncated account number data in field F3 of thefinancial data file.

In step 525, the data capture module 111 parses check number data fromthe financial data. The term “check number data” is used herein to referto information that can be used to identify the check, including, e.g.,a number or a sequence of letters, characters, and/or numbers. In step526, the data capture module 111 stores the check number data in fieldF10 of the financial data file, next to the account number data storedin field F10 in step 521. For example, the check number data and theaccount number data in field F10 can be separated by a dash, colon, orother suitable separator.

In step 527, the data capture module 111 truncates the check number datato remove extraneous characters such as dashes and to remove excessivecharacters, as required by field F4. For example, if field F4 only canreceive up to two bytes of data and the check number data is nine byteslong, the data capture module 111 can truncate seven bytes of data fromthe check number data. In step 528, the data capture module 111 storesthe truncated check number data in field F4 of the financial data file.

In step 530, the data capture module 111 parses routing transit numberdata from the financial data. The term “routing transit number data” isused herein to refer to information that can be used to identify thebank by or through which the check is payable, including, e.g., a numberor a sequence of letters, characters, and/or numbers. In step 533, thedata capture module 111 stores the routing transit number data in fieldF5 of the financial data file.

In step 535, the data capture module 111 determines an externalprocessing code for the check. The term “external processing code” isused herein to refer to information that can be used to uniquelyidentify a group of items. For example the external processing code canidentify certain items as return items, certain items as substitutechecks, and certain items as substitute checks for return items. In step537, the data capture module 111 stores the external processing code infield F6 of the financial data file.

In step 540, the data capture module 111 parses auxiliary on us datafrom the financial data. The term “auxiliary on us data” is used hereinto refer to information that can be used to uniquely identify a check.For example, the auxiliary on us data can comprise a serial number orother unique set of numbers, letters, and/or characters. In step 543,the data capture module 111 stores the auxiliary on us data in field F11of the financial data file.

In step 545, the data capture module 111 truncates the auxiliary on usdata to remove extraneous characters such as dashes and to remove excesscharacters, as required by field F7. For example, if field F7 can onlyreceive up to six bytes of data and the auxiliary on us data is ninebytes long, the data capture module 111 can truncate three bytes of datafrom the auxiliary on us data. In step 550, the data capture module 111stores the truncated auxiliary on us data in field F7 of the financialdata file.

In step 553, the data capture module 111 reads at least one result of animage quality analysis performed on the electronic image(s) of thecheck. In step 555, the data capture module 111 stores the image qualityanalysis result(s) in field F12 of the financial data file. The method425 then branches to step 430 (FIG. 4).

FIG. 6A and FIG. 6B are flow charts depicting a method 450 forconducting a reject/repair analysis of a financial data file usingexpanded mass data sets of the financial data file, according to anexemplary embodiment of the invention, as referred to in step 450 ofFIG. 4. The exemplary method 450 is merely illustrative and, inalternative embodiments of the invention, certain steps can be performedin a different order, performed in parallel with one another, or omittedentirely, and/or certain additional steps can be performed withoutdeparting from the scope and spirit of the invention. The method 450 isdescribed below with reference to FIGS. 1 and 6.

In step 605, the reject/repair module 118 analyzes the financial datafile for errors. For example, the reject/repair module 118 can detect anerror if a field of the financial data file is empty, comprises data inan incorrect format, or comprises the wrong data. In step 607, thereject/repair module 118 determines whether it detected an error. Ifnot, the method 450 branches to step 455 (FIG. 4). If the reject/repairmodule 118 detects an error, the method 450 branches to step 610.

In step 610, the reject/repair module 118 identifies the image file(s)corresponding to the financial data file. For example, the reject/repairmodule 118 can identify the image file(s) with the same file name,sequence number, or identification number as the financial data file. Instep 615, the reject/repair module 118 presents the image(s) identifiedin step 610 on the display 119 for viewing by a user. In step 620, thereject/repair module 118 reads the data in fields F1 (amount data), F5(routing transit number data), and F6 (external process code) of thefinancial data file. In step 625, the reject/repair module 118 presentsthe data from fields F1, F5, and F6 of the financial data file on thedisplay 119 for viewing by the user.

In steps 630-665, the reject/repair module 118 presents the untruncatedfinancial data, i.e., the financial data in fields F10 and F11 of thefinancial data file, in fields F2, F3, F4, and F7 on the display 119.

In step 630, the reject/repair module 118 reads and parses the processcontrol data from field F10 of the financial data file. In step 635, thereject/repair module 118 presents the parsed process control data fromfield F10 in field F2 on the display 119. Thus, the untruncated processcontrol data from field F10 is displayed in field F2.

In step 640, the reject/repair module 118 reads and parses the accountnumber data from field F10 of the financial data file. In step 645, thereject/repair module 118 presents the parsed account number data fromfield F10 in field F3 on the display 119. Thus, the untruncated accountnumber data from field F10 is displayed in field F3.

In step 650, the reject/repair module 118 reads and parses the checknumber data from field F10 of the financial data file. In step 655, thereject/repair module 118 presents the parsed check number data fromfield F10 in field F4 on the display 119. Thus, the untruncated checknumber data from field F10 is displayed in field F4.

In step 660, the reject/repair module 118 reads the auxiliary on us datafrom field F11 of the financial data file. In step 665, thereject/repair module 118 presents the auxiliary on us data from fieldF11 in field F7 on the display 119. Thus, the untruncated auxiliary onus data from field F11 is displayed in field F7.

By presenting the untruncated financial data in the display 119, thereject/repair module 118 allows a user to evaluate and correct errors inthe financial data file using the complete MICR data from the originalpaper check. The reject/repair module 118 also allows a user to correcterrors in both the truncated and untruncated data in the financial datafile. In step 670, the user compares the displayed financial data withthe displayed electronic check image(s) to determine how to correct thefinancial data file error. The user can correct the data in the display119 by inputting the correct data into the reject/repair module via akeyboard 120 or another input device. For example, where a displayeddata field is empty but the displayed image of the check comprises datacorresponding to the data field, the user can enter the financial datafrom the displayed image into the displayed data field.

In steps 675-695, the reject/repair module 118 stores the corrected datain the financial data file. In step 675, the reject/repair module 118determines whether the corrected data is in field F2 in the display 119.If so, the method 450 branches to step 676. In step 676, thereject/repair module 118 stores the corrected process control data inplace of the process control data in field F10 of the financial datafile. In step 677, the reject/repair module 118 truncates the correctedprocess control data, as described above in conjunction with FIG. 5,step 517. In step 678, the reject/repair module 118 stores thetruncated, corrected process control data in field F2 in the financialdata file, and the method 450 continues to step 455 (FIG. 4).

If the reject/repair module 118 determines in step 675 that thecorrected data is not in field F2, then the method 450 branches to step680. In step 680, the reject/repair module 118 determines whether thecorrected data is in field F3 in the display 119. If so, the method 450branches to step 681. In step 681, the reject/repair module 118 storesthe corrected account number data in place of the account number data infield F10 of the financial data file. In step 682, the reject/repairmodule 118 truncates the account number data, as described above inconjunction with FIG. 5, step 522. In step 683, the reject/repair module118 stores the truncated, corrected account number data in field F3 inthe financial data file, and the method 450 continues to step 455 (FIG.4).

If the reject/repair module 118 determines in step 680 that thecorrected data is not in field F3, then the method 450 branches to step685. In step 685, the reject/repair module 118 determines whether thecorrected data is in field F4 in the display 119. If so, the method 450branches to step 686. In step 686, the reject/repair module 118 storesthe corrected check number data in place of the check number data infield F10 of the financial data file. In step 687, the reject/repairmodule 118 truncates the check number data, as described above inconjunction with FIG. 5, step 527. In step 688, the reject/repair module118 stores the truncated, corrected check number data in field F4 in thefinancial data file, and the method 450 continues to step 455 (FIG. 4).

If the reject/repair module 118 determines in step 685 that thecorrected data is not in field F4, then the method 450 branches to step690. In step 690, the reject/repair module 118 determines whether thecorrected data is in field F7 in the display 119. If so, the method 450branches to step 691. In step 691, the reject/repair module 118 storesthe corrected auxiliary on us data in place of the auxiliary on us datain field F11 of the financial data file. In step 692, the reject/repairmodule 118 truncates the auxiliary on us data, as described above inconjunction with FIG. 5, step 545. In step 693, the reject/repair module118 stores the truncated, corrected auxiliary on us data in field F7 inthe financial data file, and the method 450 continues to step 455 (FIG.4).

If the reject/repair module 118 determines in step 690 that thecorrected data is not in field F7, then the method 450 branches to step695. In step 695, the reject/repair module 118 stores the corrected datain the corresponding field in the financial data file. For example, ifthe corrected data is in displayed field F1, F5, or F6, thereject/repair module 118 can store the corrected data in field F1, F5,or F6, respectively, of the financial data file. The method 450continues to step 455 (FIG. 4).

FIG. 7 is a flow chart depicting a method 460 for presenting a check forpayment, according to an exemplary embodiment of the invention, asreferred to in step 460 of FIG. 4. The exemplary method 460 is merelyillustrative and, in alternative embodiments of the invention, certainsteps can be performed in a different order, performed in parallel withone another, or omitted entirely, and/or certain additional steps can beperformed without departing from the scope and spirit of the invention.The method 460 is described below with reference to FIGS. 1 and 7.

In step 705, the check presentment module 116 selects a check forpresentment to the receiving institution 125. In step 710, the checkpresentment module 116 generates a substitute check form file withfields for the check's financial data, addenda data, and electronicimage(s). By entering the financial data, addenda data, and electronicimage(s) into the appropriate fields, the check presentment module 116can create a substitute check file that can be used to present asubstitute check and/or an ICL to the receiving institution 125.

In step 715, the check presentment module 116 reads the check'sfinancial data from the financial data file. In step 720, the checkpresentment module 116 identifies the image file(s) corresponding to thefinancial data file. For example, the check presentment module 116 canidentify the image file(s) with the same file name, sequence number, oridentification number as the financial data file. In step 725, the checkpresentment module 116 identifies the addenda data file(s) correspondingto the financial data file. For example, the check presentment module116 can identify the addenda data file(s) with the same file name,sequence number, or identification number as the financial data file.

In step 730, the check presentment module 116 stores the financial datafrom the financial data file, the addenda data from the identifiedaddenda data file(s), and the electronic image(s) from the identifiedimage file(s) in the appropriate fields of the substitute check file. Inthis regard, the complete, untruncated data from fields F10 and F11 ofthe financial data file is stored in the substitute check file, therebyincluding the information necessary for a substitute check to complywith the requirements of the Act. In step 733, the check presentmentmodule 116 stores the substitute check file in the substitute checkdatabase 108.

In step 735, the check presentment module 118 determines whether toselect another check for presentment to the receiving institution 125.For example, steps 705-733 can be repeated for each check associatedwith a particular receiving institution 125, whereby the associatedchecks can be presented to the receiving institution 125 at the sametime. If another check is to be selected for presentment, the method 460branches back to step 705 to repeat steps 705-733 for another check. Ifnot, the method 460 branches to step 740.

In step 740, the check presentment module 116 creates an electronic ICLfile comprising the substitute check file for each selected check. TheICL file can further comprise a series of addenda and records related tothe selected check(s). For example, the ICL file can comprise anaddendum comprising information about a bank of first deposit. Inaddition, for each bundle of substitute checks in the ICL, the ICL caninclude a bundle summary control record comprising information about thebundle. For example, the bundle summary control record can comprise abundle identification number, the number of items (substitute checkfiles) in the bundle, the value of each of the items in the bundle, andthe total value of all the items in the bundle. The ICL file also cancomprise a cover page control record comprising information about theorigin and destination of the ICL file, and a cash letter bundle summarycontrol record comprising a summary of all bundle summary controlrecords in the ICL file.

To create the ICL file in an exemplary embodiment, the check presentmentmodule 116 can organize the substitute check files (or items) into atleast one bundle. Each bundle can comprise information regarding one ormore substitute checks. The check presentment module 116 can readinformation regarding the substitute checks from the financial datafiles, addenda data files, image files, and/or substitute check filescorresponding to the substitute checks. Then, the check presentmentmodule 116 can store certain of the read information into appropriaterecord fields of the ICL file.

The check presentment module 116 also can generate and enter intoappropriate fields of the ICL file information regarding the bundle(s).For example, for each bundle, the check presentment module 116 can addup the total number of items in the bundle and the total value of allitems in the bundle and can store the total number of items, the totalvalue of all items, and the value of each item in the bundle summarycontrol record corresponding to the bundle. Similarly, the checkpresentment module 116 can add up the total value of all the items inall of the substitute check bundles (or the total value of all bundles)and can store the total value amount in the cash letter bundle summarycontrol record of the ICL file.

In step 745, the check presentment module 116 determines whether topresent the ICL electronically or via paper. If the ICL is to bepresented electronically, the method 460 branches to step 775. In step775, the check presentment module 116 electronically transmits the ICLfile to an RI computer 126 of the receiving institution 125, e.g., via anetwork (not shown).

If the check presentment module 116 determines in step 745 to presentthe ICL via paper, the method 460 branches to step 747. In step 747, thecheck presentment module 116 generates a print stream by which the ICLcan be printed onto paper. Step 747 is described in more detail belowwith reference to FIG. 8.

In step 750, the check presentment module 116 determines whether toprint the ICL locally or remotely. If the ICL is to be printed locally,the method 460 branches to step 755. In step 755, the check presentmentmodule 116 prints the ICL via a printer 117. The check presentmentmodule 116 prints the ICL using the print stream generated in step 747.More specifically, the check presentment module 116 forwards the printstream to the printer 117 for printing. The printer 117 reads the dataspecified in print stream, generates the records for printing based onthe read data, and prints the generated records in order to create theprinted ICL. In step 760, an operator of the check processing site 105collects the printed ICL, including the paper substitute check(s), fordelivery to the receiving institution 125. For example, the operator canmail or courier the printed ICL to the receiving institution 125.

If the check presentment module 116 determines in step 750 to print theICL remotely, the method 460 branches to step 770. In step 770, thecheck presentment module 116 transmits the print stream generated instep 747 to the receiving institution 125, e.g., via a network (notshown). In step 773, the receiving institution 125 prints the ICL,including the paper substitute check(s), on the RI printer 127. Morespecifically, the RI printer 127 reads the data specified in the printstream, generates the records for printing based on the read data, andprints the generated records in order to create the printed ICL.

In an alternative exemplary embodiment of the invention, the checkpresentment module 116 can generate an ICL print stream (as in step 747described below with reference to FIG. 8) without first generating anICL file or a substitute check file. The check presentment module 116can collect data directly from the image file database 113, thefinancial data file database 114, and/or the addenda data file database112 for creation of the print stream. The check presentment module 116can store the collected data in pre-defined fields of a print streamfile and transmit the print stream file to the printer 117 or the RIprinter 127 for printing.

FIG. 8 is a flow chart depicting a method 747 for generating a cashletter print stream according to an exemplary embodiment of theinvention, as referred to in step 747 of FIG. 7. The exemplary method747 is merely illustrative and, in alternative embodiments of theinvention, certain steps can be performed in a different order,performed in parallel with one another, or omitted entirely, and/orcertain additional steps can be performed without departing from thescope and spirit of the invention. The method 747 is described belowwith reference to FIGS. 1 and 8.

In step 805, a form print stream file is created and stored. The formprint stream file comprises electronic form definitions for each cashletter document to be printed in the cash letter. The cash letterdocuments include a cover page, a bundle summary, substitute checks, acash letter bundle summary, and an exception report page. The formdefinitions determine how and where to include information in the printstream for each cash letter document. For example, the form print streamfile can comprise a form definition for the print stream for each of thecover page, the bundle summary, the substitute checks, the cash letterbundle summary, and the exception report page. Each form definitiondefines data fields and their page locations, which each correspond tothe information and format required for a paper cash letter. Based onthe form definitions, the check presentment module 116 can retrieve andinput the proper information (data and/or images) into the data fieldsto create the print stream. The check presentment module 116 stores theform print stream file in a form database 130.

In step 807, the check presentment module 116 determines the file formatin which to generate the print stream. The print stream file format canvary depending on the person or entity printing the cash letter. Forexample, the file format can vary depending on the printingperson/entity's file format capabilities. A cover page control record ofthe ICL file generated in step 740 (FIG. 7) can comprise informationregarding the printing person or entity and/or the person/entity's fileformat capabilities. For example, if the cover page control recordindicates that the cash letter will be printed by a Federal ReserveBank, the print stream can be in a .AFP file format. Alternativesuitable file formats, including the .PDF file format, will be apparentto a person of skill in the art.

In steps 810-830, the check presentment module 116 creates the cashletter print stream in the appropriate file format.

In step 810, the check presentment module 116 adds a cover page to theprint stream. The cover page comprises information about the cashletter's contents, such as the number of substitute checks in the cashletter, information identifying the transmitting bank, and/orinformation identifying the receiving institution 125. For example, thecover page information can comprise information identifying the bankreceiving the cash letter by American Bankers Association (“ABA”)number, name, and address. It can further comprise print dispatchinformation, such as the bin, section, and/or courier assigned to thecash letter. To add the cover page to the print stream, the checkpresentment module 116 inserts information contained within the ICL fileinto fields of one or more of the form definitions created in step 805.For example, the check presentment module 116 can insert informationcontained within the ICL's cover page control record into correspondingfields of a cover page form definition.

In step 813, the check presentment module 116 selects a bundlecomprising at least one substitute check for inclusion in the printstream. In step 815, the check presentment module 116 adds a bundlesummary to the print stream. The bundle summary comprises informationregarding the bundle selected in step 813. For example, the bundlesummary can comprise the number of substitute checks in the bundle, thevalue of each of the substitute checks in the bundle, and the totalvalue of all substitute checks in the bundle. To add the bundle summaryto the print stream, the check presentment module 116 insertsinformation contained within the ICL file into fields of one or more ofthe form definitions created in step 805. For example, the checkpresentment module 116 can insert information contained within the ICL'sbundle summary control record into corresponding fields of a bundlesummary form definition.

In step 820, the check presentment module 116 adds the bundle'ssubstitute check(s) to the print stream. To add the substitute check(s)to the print stream, the check presentment module 116 insertsinformation contained within the ICL file into fields of one or more ofthe form definitions created in step 805. For example, for eachsubstitute check, the check presentment module 116 can insert thefinancial data, addenda data, and/or the electronic image(s)corresponding to the substitute check (and/or stored in the substitutecheck file) into corresponding fields of a substitute check formdefinition. Upon printing the generated print stream, each substitutecheck will include all of the original MICR data of the correspondingoriginal paper check and all endorsements. For example, each substitutecheck can comply with the American National Standards InstituteSpecifications for an Image Replacement Document (ANSI X9.100-140,X9.90), or other appropriate industry standards, as may change from timeto time.

In step 825, the check presentment module 116 determines whether toselect another bundle for inclusion in the print stream. For example,steps 813-820 can be repeated for each bundle to be included in the cashletter print stream. If the check presentment module 116 determines toselect another bundle, the method 747 branches back to step 813 torepeat steps 813-820 for another bundle. If the check presentment module116 determines in step 825 not to select another bundle, the method 747branches to step 830 to complete creation of the print stream.

In step 830, the check presentment module 116 adds a cash letter bundlesummary to the print stream. The cash letter bundle summary comprisesinformation about all of the bundles in the cash letter. For example,the cash letter bundle summary can comprise a total of the value of allthe bundles in the cash letter. To add the cash letter bundle summary tothe print stream, the check presentment module 116 inserts informationcontained within the ICL file into fields of one or more of the formdefinitions created in step 805. For example, the check presentmentmodule 116 can insert information from the cash letter bundle summarycontrol record into corresponding fields of a cash letter bundle summaryform definition.

In step 835, the check presentment module 116 adds an exception reportpage to the print stream. The exception report page comprisesinformation regarding any errors the check presentment module 116incurred when adding other documents to the print stream file. Forexample, the exception report information can identify a substitutecheck for which the check presentment module 116 was unable to inputcorresponding substitute check information into the substitute checkform definition. To add the exception report page to the print stream,the check presentment module 116 inserts information contained withinthe ICL file into fields of one or more of the form definitions createdin step 805. For example, the check presentment module 116 can insertinformation regarding or identifying the errors into correspondingfields of an exception report page form definition.

The method 747 continues to step 750 (FIG. 7).

As set forth above, in alternative exemplary embodiments of theinvention, the depositing institution 103 can generate an ICL forreceived checks or forward received paper checks to the capture site104. In such embodiments, the depositing institution 103 or the capturesite 104 can perform certain of the method steps described above withreference to FIGS. 4-7. For example, if the depositing institution 103generates an ICL for received checks, the depositing institution 103 cancapture, generate, and store electronic check images and financial data,as set forth in exemplary steps 405-445 of FIGS. 4, 5A, and 5B. Inaddition, the reject/repair module 213 of the depositing institution 103can perform reject/repair functions on the captured financial data, asset forth in the exemplary method 450 of FIGS. 4, 6A, and 6B. The ICLModule 215 of the depositing institution 103 can generate an ICLcomprising the captured electronic check images and financial data andcan forward the generated ICL to the check processing site 105, whichcan process the ICL in accordance with certain of the remainingexemplary steps of FIGS. 4, 7, and 8.

FIG. 9 is a block diagram depicting a print stream 900 generated inaccordance with an exemplary embodiment of the invention. First in theprint stream 900 is the cover page 905. The cover page 905 comprisesinformation regarding the cash letter's contents, such as the number ofsubstitute checks in the cash letter, information identifying thetransmitting bank, and/or information identifying the receivinginstitution 125. For example, the cover page can comprise informationidentifying the bank receiving the cash letter by ABA number, name, andaddress. It can further comprise print dispatch information, such as thebin, section, and/or courier assigned to the cash letter.

Second in the print stream is the bundle summary 910A for the firstbundle in the cash letter. The bundle summary 910A comprises informationregarding the contents of the first bundle. For example, the bundlesummary 910A can comprise the number of substitute checks in the bundle,the value of each of the substitute checks in the bundle, and the totalvalue of all substitute checks in the bundle. For each bundle ofsubstitute checks in the print stream, there is a corresponding bundlesummary 910A, 910B, 910X.

After each respective bundle summary 910A, 910B, 910X in the printstream are the substitute checks 915A, 915B, 915X listed in thecorresponding bundle summary 910A, 910B, 910X. Each substitute check cancomprise all of the original MICR data of the corresponding originalpaper check and all endorsements.

Next in the print stream 900 is the cash letter bundle summary 920. Thecash letter bundle summary 920 comprises information about all of thebundles in the cash letter. For example, the cash letter bundle summary920 can comprise a total of the value of all the bundles in the cashletter.

Last in the print stream 900 is the exception report page 925, whichcomprises information regarding any errors the check presentment module116 incurred when generating other documents in the print stream file.For example, the exception report page 925 can comprise informationidentifying a substitute check for which the check presentment module116 was unable to input corresponding substitute check information intothe substitute check form definition.

The information from the print stream 900 can be printed in order, withthe resulting printout comprising a paper cash letter. For example,printing the information from the print stream 900 depicted in FIG. 9,results in a properly formatted and ordered paper cash letter comprisingsubstitute checks and audit data. The audit data (i.e., the cover page905, the bundle summary 910A, 910B, 910X, the cash letter bundle summary920, and the exception report page 925) comprises control reports thatdetail the documents printed concurrently therewith. Thus, the auditdata provides a real-time inventory of the paper cash letter.

In an exemplary embodiment, the print stream 900 can be printed onperforated paper and passed through a bursting machine to create thepaper cash letter. Upon printing, a paper burster can separate eachprinted page at its perforations, so that each separated page comprisesa portion of the cash letter. Thus, the cover page 905, bundle summaries910A, 910B, 910X, substitute checks 915A, 915B, 915X, cash letter bundlesummary 920, and exception report page 925 can each be printed on aseparate page based on the size of the pages between the perforations.Additionally, the different components of the paper cash letter can beprinted on different color paper for easy identification.

In one embodiment of the invention, the check presentment module 116 caninstruct the printer 117 (or the RI printer 127) to print each of thedocuments on different types, colors, and/or sizes of paper. Forexample, the check presentment module 116 can instruct the printer 117(or the RI printer 127) to print the substitute checks 915A, 915B, 915Xon yellow paper and each of the other documents in the cash letter onblue paper. In yet another embodiment of the invention, the type, color,and/or size of the paper can vary depending on whether the transactionis a forward transaction or a return transaction. For example, the checkpresentment module 116 can instruct the printer 117 (or the RI printer127) to print each of the non-substitute check documents of a forwardtransaction on blue paper and each of the non-substitute check documentsof a return transaction on red paper. In an exemplary embodiment, theprint stream file form definition corresponding to each cash letterdocument can comprise a designation for a particular type, color, and/orsize of paper on which to print the corresponding cash letter document.

FIG. 10 is a block diagram depicting a cover page 1000 printed from aprint stream generated in accordance with an exemplary embodiment of theinvention. The cover page 1000 is printed on one section of a perforatedsheet of paper and comprises information regarding the cash letter'scontents. The cover page 1000 can be separated from the other sectionsof the perforated sheet by tearing the sheet at its perforations. Theexemplary cover page 1000 comprises a count 1005 of the number of itemsin the cash letter and destination information 1010 identifying thedestination of the cash letter by ABA number, name, and address. Itfurther comprises print dispatch information, such as the bin, section,and/or courier assigned to the cash letter. A person of skill in the artwill recognize that the cover page 1000 can comprise other additionalinformation related to the cash letter's contents, and/or certainillustrated information can be removed from the cover page 1000, withoutdeparting from the scope and spirit of the invention.

FIG. 11 is a block diagram depicting a bundle summary page 1100 printedfrom a print stream generated in accordance with an exemplary embodimentof the invention. The bundle summary page 1100 is printed on threesections of a perforated sheet of paper. The sections of the bundlesummary page 1100 can be separated from one another by tearing the sheetat its perforations. The exemplary bundle summary page 1100 comprises acount 1105 of the number of items in bundle A, the value of each of theitems in the bundle, and the total value 1110 of all items in thebundle. It also includes information identifying the destination of thebundle summary page 1100 by bank name and address. A person of skill inthe art will recognize that the bundle summary page 1100 can compriseother additional information related to the items in bundle A, and/orcertain illustrated information can be removed from the bundle summarypage 1100, without departing from the scope and spirit of the invention.

FIG. 12 is a block diagram depicting a substitute check page 1200printed from a print stream generated in accordance with an exemplaryembodiment of the invention. The substitute check page 1200 comprisesmultiple substitute checks, printed front and back, on perforated paper.As shown in FIG. 12, three substitute checks can be printed on a singlepiece of perforated paper, which can be separated at its perforations toproduce individual pages for each substitute check.

FIG. 13 is a block diagram depicting a cash letter bundle summary page1300 printed from a print stream generated in accordance with anexemplary embodiment of the invention. The cash letter bundle summarypage 1300 is printed on three sections of a perforated sheet of paper.The sections of the cash letter bundle summary page 1300 can beseparated from one another by tearing the sheet at its perforations. Theexemplary cash letter bundle summary page 1300 comprises informationregarding each bundle in the cash letter, including a bundle ID, bundlenumber, item count, and total value amount for each bundle in the cashletter. The cash letter bundle summary page 1300 comprises a total itemcount 1305 and a total value amount for all the bundles 1310. Inaddition, the cash letter bundle summary page 1300 comprises informationidentifying the destination of the cash letter bundle summary page 1300by bank ABA number, name, and address. A person of skill in the art willrecognize that the cash letter bundle summary page 1300 can compriseother additional information related to the cash letter bundles, and/orcertain illustrated information can be removed from the cash letterbundle summary page 1300, without departing from the scope and spirit ofthe invention.

FIG. 14 is a block diagram depicting an exception report page 1400printed from a print stream generated in accordance with an exemplaryembodiment of the invention. The exception report page 1400 is printedon one section of a perforated sheet of paper. The exception report page1400 can be separated from the other sections of the perforated sheet bytearing the sheet at its perforations. The exemplary exception reportpage 1400 comprises information regarding errors the check presentmentmodule incurred when generating other documents in the print streamfile. The errors relate to three documents, which are identified byrouting transit number, sequence number, amount, and bundle ID. Inaddition, a reason for each error is provided. A person of skill in theart will recognize that the exception report page 1400 can compriseother additional information related to the errors, and/or certainillustrated information can be removed from the exception report page1400, without departing from the scope and spirit of the invention.

FIG. 15 is a flow chart depicting a method 1500 for verifying cashletter printing, according to an exemplary embodiment of the invention.The exemplary method 1500 is merely illustrative and, in alternativeembodiments of the invention, certain steps can be performed in adifferent order, performed in parallel with one another, or omittedentirely, and/or certain additional steps can be performed withoutdeparting from the scope and spirit of the invention. The method 1500 isdescribed below with reference to FIGS. 1 and 15.

In step 1505, the check presentment module 116 stores informationregarding multiple ICLs to be printed in a print request record. Theterm “record” is used herein to refer to a set of electronic data,including, without limitation, a table, a file, and a part of a table orfile. The information stored in the print request record includes datathat uniquely identifies each ICL to be printed. For example, for eachICL, the print request record can include a total value of the items inthe ICL, an ABA number of the bank that will receive the printed ICL, atotal number of bundles in the ICL, and/or a total number of items inthe ICL. In certain exemplary embodiments, the check presentment module116 can store the print request record in a print database 135 of thecheck processor 109.

In step 1510, at least a portion of the ICLs are printed. Each printedICL includes a machine-readable identifier, such as a barcode, with atleast a portion of the information stored in the print request record.For example, one of the printers 117 and 127 can print the ICLs uponreceiving an ICL print stream from the check presentment module 116,substantially as described above in connection with FIGS. 7 and 8. Theprint stream can include information necessary for printing themachine-readable identifier, including at least a portion of theinformation stored in the print request record. In certain exemplaryembodiments, a cover page of each printed ICL can include the printedmachine-readable identifier.

In step 1515, the check presentment module 116 reads the information ineach of the printed machine-readable identifiers of the printed ICLs. Incertain exemplary embodiments, the check presentment module 116 canreceive the information from one or more barcode scanners (not shown) orother data readers at the print location (i.e., the check processingsite 105 or the receiving institution 125). For example, an operator atthe print location can scan a printed barcode after the ICL containingthe barcode is done printing.

In step 1520, the check presentment module 116 stores the informationread in step 1515 in a printed ICL record. In certain exemplaryembodiments, the check presentment module 116 can store the printed ICLrecord in the print database 135. In step 1525, the check presentmentmodule 116 compares the information in the print request record and theprinted ICL record. Based on that comparison, in step 1530, the checkpresentment module 116 identifies the ICLs, if any, that have not beenprinted (in step 1510).

For example, if information identifying a particular ICL is present inthe print request record but not in the printed ICL record, the checkpresentment module 116 can identify the ICL as not having been printed.Similarly, if information identifying a particular ICL is present inboth the print request record and the printed ICL record, the checkpresentment module 116 can not identify the ICL.

In step 1535, the check presentment module 116 outputs an alertincluding information regarding the ICLs identified in step 1530. Forexample, the check presentment module 116 can output a visual and/oraudible alert via one or more output devices at the check processingsite 105 and/or the receiving institution 125. In certain exemplaryembodiments, an operator receiving the alert can investigate why theidentified ICLs failed to print. For example, the operator can identifya printing error that caused the printing failure. The operator also caninstruct the check presentment module 116 to attempt to re-print theICL.

In certain exemplary embodiments, an operator can instruct the checkpresentment module 116 to perform one or more of the comparison,identification, and alert functions of steps 1525-1535 via the keyboard120 or another input device associated with the check processor 109and/or the receiving institution 125. Alternatively, the checkpresentment module 116 can be configured to automatically perform thesefunctions. For example, the check presentment module 116 can beconfigured to automatically perform these functions at specified timeintervals.

Although the method 1500 has been described herein with regard to ICLs,a person of ordinary skill in the art having the benefit of the presentdisclosure will recognize that the method 1500 also can be applied toverify printing of items and/or item bundles. For example, the ICLprinted in step 1510 can include a machine-readable identifier for eachitem and/or bundle. The machine-readable identifier can includeinformation uniquely identifying the item and/or bundle. The checkpresentment module 116 can compare information in each printedmachine-readable identifier with information in the print request recordto determine whether each item and/or bundle has been printed.

FIG. 16 is a flow chart depicting a method 1600 for identifyingduplicate printed paper cash letters, according to an exemplaryembodiment of the invention. The exemplary method 1600 is merelyillustrative and, in alternative embodiments of the invention, certainsteps can be performed in a different order, performed in parallel withone another, or omitted entirely, and/or certain additional steps can beperformed without departing from the scope and spirit of the invention.The method 1600 is described below with reference to FIGS. 1 and 16.

In step 1605, the check presentment module 116 generates a print streamfor an ICL. The print stream includes information necessary for printinga machine-readable identifier, such as a barcode, with informationuniquely identifying the ICL, such as a total value of the items in theICL, an ABA number of the bank that will receive the printed ICL, atotal number of bundles in the ICL, and/or a total number of items inthe ICL. For example, the check presentment module 116 can generate theICL print stream substantially as described above in connection withFIGS. 7 and 8. In certain exemplary embodiments, the print stream caninclude an ICL cover page including the machine-readable identifier.

In step 1610, the check presentment module 116 prints the ICL, includingthe machine-readable identifier. For example, the check presentmentmodule 116 can transmit the print stream to one of the printers 117 and127 for printing. In step 1615, the check presentment module 116 readsthe information in the printed machine-readable identifier of theprinted ICL. In certain exemplary embodiments, the check presentmentmodule 116 can receive the information from a barcode scanner (notshown) or other data reader at the print location (i.e., the checkprocessing site 105 or the receiving institution 125). For example, anoperator at the print location can scan a printed barcode after the ICLcontaining the barcode is done printing.

In step 1620, the check presentment module 116 compares the readinformation with information in a printed ICL record. As described abovein connection with FIG. 15, the printed ICL record includes informationuniquely identifying ICLs that already have been printed. Thisinformation in the printed ICL record originated from data read from themachine-readable identifiers associated with each printed ICL uponcompletion of printing of the ICL. For example, for each printed ICL,the information can include a total value of the items in the ICL, anABA number of the bank that will receive the printed ICL, a total numberof bundles in the ICL, and/or a total number of items in the ICL.

Based on the comparison in step 1620, in step 1625, the checkpresentment module 116 determines whether the ICL was printed twice,i.e., whether the printed cash letter is a duplicate of an alreadyprinted ICL. For example, if the printed ICL record includes informationidentifying the ICL, then the check presentment module 116 can determinethat the ICL was printed twice. Similarly, if the printed ICL recorddoes not include information identifying the ICL, then the checkpresentment module 116 can determine that the ICL was not printed twice.

If the check presentment module 116 determines in step 1625 that the ICLwas printed twice, the method 1600 branches to step 1630. In step 1630,the check presentment module 116 outputs an alert identifying theduplicate printed ICL. For example, the check presentment module 116 canoutput a visual and/or audible alert via one or more output devices atthe check processing site 105 and/or the receiving institution 125. Incertain exemplary embodiments, an operator receiving the alert candiscard the printed ICL.

If the check presentment module 116 determines in step 1625 that the ICLwas not printed twice, then the method 1600 branches to step 1635. Instep 1635, the check presentment module 116 stores the information readin step 1615 in the printed ICL record, so that the check presentmentmodule 116 can identify any subsequently printed duplicates of theprinted ICL by comparing information in the duplicates with theinformation stored in the printed ICL record.

Although the method 1600 has been described herein with regard to ICLs,a person of ordinary skill in the art having the benefit of the presentdisclosure will recognize that the method 1600 also can be applied toidentify duplicate printed items and/or duplicate printed item bundles.For example, the print stream generated in step 1605 can include amachine-readable identifier for each item and/or bundle. Themachine-readable identifier can include information uniquely identifyingthe item and/or bundle. The check presentment module 116 can compareinformation in a printed machine-readable identifier with information inthe printed ICL record to determine whether each item and/or bundle is aduplicate.

The invention can be used with computer hardware and software thatperforms the methods and processing functions described above. As willbe appreciated by those skilled in the art, the systems, methods, andprocedures described herein can be embodied in a programmable computer,computer executable software, or digital circuitry. The software can bestored on computer readable media. For example, computer readable mediacan include a floppy disk, RAM, ROM, hard disk, removable media, flashmemory, memory stick, optical media, magneto-optical media, CD-ROM, etc.Digital circuitry can include integrated circuits, gate arrays, buildingblock logic, field programmable gate arrays (FPGA), etc.

Although specific embodiments of the invention have been described abovein detail, the description is merely for purposes of illustration. Itshould be appreciated, therefore, that many aspects of the inventionwere described above by way of example only and are not intended asrequired or essential elements of the invention unless explicitly statedotherwise. Various modifications of, and equivalent steps correspondingto, the disclosed aspects of the exemplary embodiments, in addition tothose described above, can be made by those skilled in the art withoutdeparting from the spirit and scope of the invention defined in thefollowing claims, the scope of which is to be accorded the broadestinterpretation so as to encompass such modifications and equivalentstructures.

1. A computer-implemented method for verifying printing of an electronicimage cash letter (“ICL”), comprising the steps of: storing informationregarding multiple ICLs to be printed in a first record; readinginformation in each of a plurality of printed machine-readableidentifiers, each printed machine-readable identifier being associatedwith a printed one of the ICLs; storing the read information in a secondrecord; identifying, by a check presentment module, any of the ICLs thathave not been printed by comparing the information in the first recordwith the information in the second record; and causing, by the checkpresentment module, information regarding the identified ICLs to bedisplayed, wherein the check presentment module is implemented in atleast one computer system that comprises instructions stored in amachine-readable medium and a processor that executes the instructions.2. The method of claim 1, wherein each printed machine-readableidentifier comprises a barcode.
 3. The method of claim 1, wherein thestep of causing information regarding the identified ICLs to bedisplayed comprises outputting an alert including information regardingthe identified ICLs.
 4. The method of claim 1, wherein, for each of themultiple ICLs to be printed, the information stored in the first recordcomprises information uniquely identifying the ICL.
 5. The method ofclaim 4, wherein the information uniquely identifying the ICL comprisesat least one of a total value of items in the ICL, an ABA number of abank that will receive a printed copy of the ICL, a total number of itembundles in the ICL, and a total number of items in the ICL.
 6. Themethod of claim 1, wherein, for each printed machine-readableidentifier, the information stored in the second record comprisesinformation uniquely identifying the one of the ICLs associated with theprinted machine-readable identifier.
 7. The method of claim 6, whereinthe information uniquely identifying the one of the ICLs comprises atleast one of a total value of items in the ICL, an ABA number of a bankthat will receive a printed copy of the ICL, a total number of itembundles in the ICL, and a total number of items in the ICL.
 8. Themethod of claim 1, wherein each printed machine-readable identifier isdisposed on a cover page of the one of the ICLs associated with theprinted machine-readable identifier.
 9. The method of claim 1, furthercomprising the steps of: for each of the printed machine-readableidentifiers, prior to storing the read information in the second record,determining whether information regarding the one of the ICLs associatedwith the printed machine-readable identifier already is stored in thesecond record; and in response to determining that information regardingthe one of the ICLs associated with the printed machine-readableidentifier already is stored in the second record, outputting an alertadvising an operator that the one of the ICLs was printed twice.
 10. Acomputer-implemented method for verifying printing of an electronicimage cash letter (“ICL”), comprising the steps of: storing, in a firstrecord, information uniquely identifying each of multiple ICLs to beprinted, the information stored for each ICL comprising at least one ofa total value of items in the ICL, an ABA number of a bank that willreceive a printed copy of the ICL, a total number of item bundles in theICL, and a total number of items in the ICL; reading information in eachof a plurality of printed machine-readable identifiers, each printedmachine-readable identifier being disposed on a printed one of the ICLs;storing the read information in a second record; determining, by a checkpresentment module, whether any of the ICLs have not been printed bycomparing the information in the first record with the information inthe second record; and in response to determining that at least one ofthe ICLs has not been printed, causing, by the check presentment module,an output of an alert advising an operator that the at least one of theICLs has not been printed, wherein the check presentment module isimplemented in at least one computer system that comprises instructionsstored in a machine-readable medium and a processor that executes theinstructions.
 11. The method of claim 10, wherein each printedmachine-readable identifier comprises a barcode.
 12. The method of claim10, wherein, for each machine-readable identifier, the informationstored in the second record comprises information uniquely identifyingthe printed one of the ICLs on which the machine-readable identifier isdisposed.
 13. The method of claim 12, wherein the information, stored inthe second record, which uniquely identifies the printed one of the ICLscomprises at least one of a total value of items in the ICL, an ABAnumber of a bank that will receive a printed copy of the ICL, a totalnumber of item bundles in the ICL, and a total number of items in theICL.
 14. The method of claim 10, further comprising the steps of: priorto storing the read information in the second record, determiningwhether information regarding the one of the ICLs associated with theprinted machine-readable identifier already is stored in the secondrecord; and in response to determining that information regarding theone of the ICLs associated with the printed machine-readable identifieralready is stored in the second record, outputting an alert notifying anoperator that the one of the ICLs was printed twice.
 15. The method ofclaim 10, wherein each printed machine-readable identifier is disposedon a cover page of the one of the ICLs associated with the printedbarcode.
 16. The method of claim 10, wherein the alert includesinformation uniquely identifying the at least one of the ICLs has notbeen printed.
 17. A computer-implemented method for verifying printingof an electronic image cash letter (“ICL”), comprising the steps of:storing information regarding multiple ICLs to be printed in a record;reading information in each of a plurality of printed machine-readableidentifiers, each printed machine-readable identifier being associatedwith a printed one of the ICLs; identifying, by a check presentmentmodule, any of the ICLs that have not been printed by comparing the readinformation with the information stored in the record; and causing, bythe check presentment module, information regarding the identified ICLsto be displayed, wherein the check presentment module is implemented inat least one computer system that comprises instructions stored in amachine-readable medium and a processor that executes the instructions.18. The method of claim 17, wherein each printed machine-readableidentifier comprises a barcode.
 19. The method of claim 17, wherein thestep of causing information regarding the identified ICLs to bedisplayed comprises outputting an alert including information regardingthe identified ICLs.
 20. The method of claim 17, wherein, for each ofthe multiple ICLs to be printed, the information stored in the recordcomprises information uniquely identifying the ICL, the informationuniquely identifying the ICL comprising at least one of a total value ofitems in the ICL, an ABA number of a bank that will receive a printedcopy of the ICL, a total number of item bundles in the ICL, and a totalnumber of items in the ICL.
 21. The method of claim 17, wherein eachprinted machine-readable identifier is disposed on a cover page of theone of the ICLs associated with the printed machine-readable identifier.